Docs update: Clarifies only executing runs count towards concurrency#1760
Docs update: Clarifies only executing runs count towards concurrency#1760
Conversation
|
WalkthroughThe pull request updates the task execution documentation to clarify how concurrency limits are applied. It explicitly states that only actively executing runs are counted towards the concurrency limits, while runs in a delayed or queued state do not consume concurrency slots until they start executing. No changes to exported or public entities were made. Changes
Possibly Related PRs
Poem
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (1)
⏰ Context from checks skipped due to timeout of 90000ms (1)
🔇 Additional comments (1)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
Small text update to clarify only executing runs count towards concurrency
Summary by CodeRabbit